build(deps-dev): bump the development-minor-and-patch group across 1 directory with 2 updates#145
Conversation
…directory with 2 updates Bumps the development-minor-and-patch group with 2 updates in the / directory: [oxfmt](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxfmt) and [oxlint](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxlint). Updates `oxfmt` from 0.55.0 to 0.56.0 - [Release notes](https://github.com/oxc-project/oxc/releases) - [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxfmt/CHANGELOG.md) - [Commits](https://github.com/oxc-project/oxc/commits/oxfmt_v0.56.0/npm/oxfmt) Updates `oxlint` from 1.70.0 to 1.71.0 - [Release notes](https://github.com/oxc-project/oxc/releases) - [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxlint/CHANGELOG.md) - [Commits](https://github.com/oxc-project/oxc/commits/oxlint_v1.71.0/npm/oxlint) --- updated-dependencies: - dependency-name: oxfmt dependency-version: 0.56.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development-minor-and-patch - dependency-name: oxlint dependency-version: 1.71.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development-minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
Codex review: needs maintainer review before merge. Reviewed June 29, 2026, 12:12 PM ET / 16:12 UTC. Summary Reproducibility: not applicable. This PR is dependency maintenance rather than a bug report. The relevant verification is lockfile/package diff review plus CI and dependency review. Review metrics: 3 noteworthy metrics.
Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Rank-up moves:
Risk before merge
Maintainer options:
Next step before merge
Security Review detailsBest possible solution: Land the narrow dependency update after normal CI, dependency-review, and CODEOWNERS approval, or close it only if maintainers choose to skip this OXC toolchain version. Do we have a high-confidence way to reproduce the issue? Not applicable: this PR is dependency maintenance rather than a bug report. The relevant verification is lockfile/package diff review plus CI and dependency review. Is this the best way to solve the issue? Yes: a package.json and pnpm-lock update is the narrow maintainable path for updating the repo's OXC formatter/linter dev tooling. I did not find duplicated behavior or a product decision hidden in the diff. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against 24763d26cdff. Label changesLabel changes:
Label justifications:
Evidence reviewedWhat I checked:
Likely related people:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. How this review workflow works
|
Bumps the development-minor-and-patch group with 2 updates in the / directory: oxfmt and oxlint.
Updates
oxfmtfrom 0.55.0 to 0.56.0Changelog
Sourced from oxfmt's changelog.
Commits
c4be770release(apps): oxlint v1.71.0 && oxfmt v0.56.0 (#23707)Updates
oxlintfrom 1.70.0 to 1.71.0Release notes
Sourced from oxlint's releases.
... (truncated)
Changelog
Sourced from oxlint's changelog.
Commits
c4be770release(apps): oxlint v1.71.0 && oxfmt v0.56.0 (#23707)0dc2405feat(linter): add schema foreslint/no-restricted-properties(#23619)b638d0efeat(linter): add schema fornode/callback-return(#23615)6d355abrefactor(linter): removenumber_as_object_schemahelper (#23614)eb8bedcfeat(linter): add schema forimport/extensions(#23557)46f3625feat(linter): implement node/no-sync rule (#23589)953c7b3refactor(linter): makeunicorn/numeric-separators-styleoptionsu32(#23558)b01739afeat(linter): add schema forunicorn/numeric-separators-style(#23554)68afd2afeat(linter/node): implementno-mixed-requiresrule (#23539)b08e9f5refactor(linter): re-enable schema for `jsx_a11y/no-noninteractive-element-in...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions